View Issue Details

IDProjectCategoryView StatusLast Update
0001047T99X171.00 SKB EagleSW Issuepublic2021-12-23 17:39
Reporter(ALTech) Jason ParkAssigned To(SW) Kerwin Chen Due Date
PriorityhighSeveritys2-severeReproducibilityhave not tried
Status closedResolutionunable to reproduce 
Summary0001047: [BFX_AT100][BTVV-1951] VOC is increasing for Voice Search on Smart3.
Descriptionhi kerwin

as send a mail, skb VOC is increasing about voice search fail.
so I create a ticket

1 week before : 3
2 week before : 11
3 week before : 15
4 week before : 6
 this week :15
 Total 50.

we need to explain or to solve this issue. please see a log.

as specification, BT is disconnect within 18 hours. However, many SKB user have some problem about Voice search fail or don’t work RCU.
So we need to make a plan for solving or explanation about this issue.

  1. Which case does BT is disconnected except Idle Timeout ?
  2. As explanation on mantis, BT is connecting within 10s. If it is right, why does SKB user meet many Issue about BT problem?
       You need to do brain storms about SKB VOC.
       Which case does we can’t connect to BT again? Please give your opinion as variety . since we need to explain it to SKB user about many case.
   3. As you know , BT10 has some problem to connection.
       Please explain to us again with a technical note.
       Case TVstorm , BFX-AT100 is difficult to pairing with BA01 RCU , since it is searching with using BT address(oui) area in Dae-woo building.
      Since Intek Smart3 is used with HCI Module (MD-BRC101). So this module is used in a similar area. (401920-100001 ~ 401920-100044 , 401920-111480 ~ 401920-111520)
      According to, TVstorm applied Major Device Class in V15.520.8. we can distinguish BT device but although set filter as 0x400, we seem meet A2DP searching fail
       as talked upper, please explain it with a technical not for SKB manager.

      please agenda #1 , #2 . we need to feedback more fast.


TagsNo tags attached.
Attach Tags

Users monitoring this issue

Activities

(ALTech) Jason Park

2020-12-07 18:41

developer  

(ALTech) Jason Park

2020-12-08 11:02

developer   ~0005338

Last edited: 2020-12-08 11:04

hi kerwin

according to SKB explanation, it is increasing VOC Item at 12/7. so we especially investigate a log from 12/7.

after reboot box and repairing with RCU, It works well in many case. so Could you check whether if is this related to android BT Upgrade service ?

(SW) Kerwin Chen

2020-12-08 11:45

developer   ~0005341

Hi Jason,

I am still checking for the logs and will update later.
But I don't understand about you question about "BT Upgrade service".
Foxconn don't have any process to update android BT service on Android P.
Thanks !

(SW) Kerwin Chen

2020-12-08 14:20

developer   ~0005343

Hi Jason,

I found there is a tombstone in the log files which is similar with another issue on BTF. (https://mantis.cnsbg.foxconn.com/vaas/view.php?id=947)
We already have a workaround solution on BTF to avoid audio server crash.
It can be also applied to Android P.
However, we don't have any update plan on Android P of ATV model, right ?

I think the root cause is remaining capacity of battery is low.
Smart3 is launched for more than 1 year, for some users it is the time to change battery.
This is why VoC issue is increasing recently.
Please check it with SKB and end users.
Thanks !

(ALTech) Jason Park

2020-12-08 14:35

developer   ~0005344

Last edited: 2020-12-08 14:56

hi kerwin

although you find tomstone, I can't find it in a log.

this issue is don't work for voice search and don't pairing with RCU again. you think also second issue(don't pairing) is related to your comment ( tombstone issue) ?

as inform to you, we have a chance to upgrade in UHD4 . So please update it in advance.
case ATV, We will have a chance to upgrade as android 10 soon.

(SW) Kerwin Chen

2020-12-08 15:04

developer   ~0005345

Hi Jason,

Please search for keyword "android.hardware.audio@2.0-service" in tombstone files.
And for sure, we will apply it to AOSP model since it is for NUGU voice.
Thanks !

(ALTech) Jason Park

2020-12-08 15:25

developer   ~0005347

Last edited: 2020-12-08 15:42

hi kerwin.

sorry to bother you , my talking is for main.log. it don't find it in main.log. it isn't a big issue. please ignore my talking.
mantis 947. We already fix it and commit to BitBucket, the fix will be included in next release. Can you give a commit item? since I have to leave some comment on SKB voc with an explanation.
if happen audio crashed issue, RCU don't pairing again if RCU battery's capacity is full?

(SW) Kerwin Chen

2020-12-08 16:34

developer   ~0005348

Hi Jason,

The workaround solution on BTF is to avoid audio server crash.
Actually, root cause is "RCU battery" which results in RCU disconnected with STB.
If RCU battery always has enough capacity, RCU will be always connected and we don't need the workaround solution.
Thanks !

(ALTech) Jason Park

2020-12-09 16:38

developer   ~0005386

hi kerwin

as you know it, we also make new fw for UHD4_522.
So please apply this patch for UHD4_522.

(ALTech) Jason Park

2020-12-09 16:53

developer   ~0005387

hi kerwin.

SKB RCU Manager ask it to FXN below question.

. skb manager think there is no problem about battery capacity. since they also check a log as keyword" battery".
. please explain it regarding to a relationship between audio server crash and Voice research. why does audio crash affected for audio voice search ?
. please explain it regarding to a relationship between rcu disconnection and audio server crash.
   ( when push voice search button in rcu disconnected, IR Code is transmitted for showing a guide for RCU repairing )

as you feel upper comment, skb manager think it is a critical item in VOC. So when you give an answer to us, please give a right answer with a technical explanation.

.

(SW) Kerwin Chen

2020-12-09 17:12

developer   ~0005388

Hi Jason,

. skb manager think there is no problem about battery capacity. since they also check a log as keyword" battery".
==> I don't know how SKB check about battery because I don't find it in log files. From the log file, audio server crash at the same point with Mantis947.

. please explain it regarding to a relationship between audio server crash and Voice research. why does audio crash affected for audio voice search ?
==> Audio HAL reads data from RCU after pressing NUGU button. If RCU is disconnected suddenly, driver will be removed automatically. Audio HAL keep use the same pointer to read data.
As a result, there is a NULL pointer access in audio HAL.

. please explain it regarding to a relationship between rcu disconnection and audio server crash.
   ( when push voice search button in rcu disconnected, IR Code is transmitted for showing a guide for RCU repairing )
==> RCU is disconnected suddenly, not unpair. Pairing dialog will never be shown.

(ALTech) Jason Park

2020-12-10 18:15

developer   ~0005410

hi kerwin

I don't want to play a ping-pong game with skb manager about this issue. please check a log again regarding to BT disconnect reason.
please see skb manager feedback.
. I don't know how SKB check about battery because I don't find it in log files
--> whenever push homeUI button of RCU, it is transmitted to system property as normal/low/empty.
 you can find as keyword ( STBGlobal: getBattery - property : 2, eBATTERY : NORMAL_BATTERY ) in a log.
or you also see in BAS Profile.
Finsky : [2] aafz.handleMessage(4): SCH: DeviceState: DeviceState{currentTime=1607266852599, isCharging=true, isIdle=false, netAny=true, netNotRoaming=true, netUnmetered=true, batteryPercent=42.0}

==> RCU is disconnected suddenly, not unpair. Pairing dialog will never be shown.
when push voice search button in rcu disconnected, as transmitted as battery empty key value, it is shown pop-up window for changing a battery.
if don't see it,, it guess it is related to mantis 914.
https://mantis.cnsbg.foxconn.com/vaas/view.php?id=914

SKB manager think if this issue is related to BT Disconnection, disconnection's reason isn't a low battery.

(SW) Kerwin Chen

2020-12-10 19:16

developer   ~0005411

Hi Jason,

I don't think the 2 log files(main.log, main.log.1) are enough to present user's issue.
Because the duration of main.log/main.log.1 are too short.
It contains messages within minutes.
This is why you can't find tombstone in main.log/main.log.1.

From our previous project in Taiwan, we also had experience that RCU needs more power before it start to send voice data.
At that time, BT RCU is disconnected suddenly.

(ALTech) Jason Park

2020-12-11 08:09

developer   ~0005416

hi kerwin

I understand a comment. but SKB service man tried to capture a log when issue happen. so according to skb manager talking, a capacity of battery isn't low in capturinged log.
so as your comment, if may don't find about tombstone in main.log/log1, why does BT is disconnected ? but skb user can pairing it again. this issue is resolved.
and I think also this issue isn't related to Low battery. so BT disconnected issue isn't a real reason about this issue.

(ALTech) Jason Park

2020-12-14 11:08

developer   ~0005443

hi kerwin

please give your feedback more. we need to you about my question and more explanation of this issue.

(ALTech) Jason Park

2020-12-15 14:01

developer   ~0005465

hi kerwin

this issue is very a critical issue in a field.. so please give your feedback.

(SW) Kerwin Chen

2021-12-23 17:39

developer   ~0009075

not reproducible on latest version

Issue History

Date Modified Username Field Change
2020-12-07 18:41 (ALTech) Jason Park New Issue
2020-12-07 18:41 (ALTech) Jason Park File Added: Smart3 STB 음성검색불가 VoC.zip
2020-12-07 18:41 (ALTech) Jason Park Issue Monitored: (ALTech) Wooshin Kang
2020-12-07 18:41 (ALTech) Jason Park Issue Monitored: (ALTech) SY Yoon
2020-12-07 18:41 (ALTech) Jason Park Issue Monitored: (ALTech) Younkwang Jung
2020-12-07 18:42 (ALTech) Jason Park Assigned To => (SW) Kerwin Chen
2020-12-07 18:42 (ALTech) Jason Park Status new => assigned
2020-12-07 18:44 (ALTech) Jason Park Description Updated
2020-12-07 18:44 (ALTech) Jason Park Steps to Reproduce Updated
2020-12-08 11:02 (ALTech) Jason Park Note Added: 0005338
2020-12-08 11:04 (ALTech) Jason Park Note Edited: 0005338
2020-12-08 11:45 (SW) Kerwin Chen Note Added: 0005341
2020-12-08 14:20 (SW) Kerwin Chen Note Added: 0005343
2020-12-08 14:20 (SW) Kerwin Chen Assigned To (SW) Kerwin Chen => (ALTech) Jason Park
2020-12-08 14:20 (SW) Kerwin Chen Status assigned => feedback
2020-12-08 14:35 (ALTech) Jason Park Note Added: 0005344
2020-12-08 14:42 (ALTech) Jason Park Note Edited: 0005344
2020-12-08 14:56 (ALTech) Jason Park Note Edited: 0005344
2020-12-08 14:56 (ALTech) Jason Park Assigned To (ALTech) Jason Park => (SW) Kerwin Chen
2020-12-08 14:56 (ALTech) Jason Park Status feedback => assigned
2020-12-08 15:04 (SW) Kerwin Chen Note Added: 0005345
2020-12-08 15:25 (ALTech) Jason Park Note Added: 0005347
2020-12-08 15:42 (ALTech) Jason Park Note Edited: 0005347
2020-12-08 16:34 (SW) Kerwin Chen Note Added: 0005348
2020-12-09 16:38 (ALTech) Jason Park Note Added: 0005386
2020-12-09 16:53 (ALTech) Jason Park Note Added: 0005387
2020-12-09 17:12 (SW) Kerwin Chen Note Added: 0005388
2020-12-09 17:12 (SW) Kerwin Chen Assigned To (SW) Kerwin Chen => (ALTech) Jason Park
2020-12-09 17:12 (SW) Kerwin Chen Status assigned => feedback
2020-12-10 18:15 (ALTech) Jason Park Note Added: 0005410
2020-12-10 18:15 (ALTech) Jason Park Assigned To (ALTech) Jason Park => (SW) Kerwin Chen
2020-12-10 18:15 (ALTech) Jason Park Status feedback => assigned
2020-12-10 19:16 (SW) Kerwin Chen Note Added: 0005411
2020-12-11 08:09 (ALTech) Jason Park Note Added: 0005416
2020-12-14 11:08 (ALTech) Jason Park Note Added: 0005443
2020-12-15 14:01 (ALTech) Jason Park Note Added: 0005465
2021-12-23 17:39 (SW) Kerwin Chen Status assigned => closed
2021-12-23 17:39 (SW) Kerwin Chen Resolution open => unable to reproduce
2021-12-23 17:39 (SW) Kerwin Chen Note Added: 0009075